Modelling Requirement Engineering
Recognizing Multiple viewpoint
Collaborative Requirement Gathering
Building the requirements model
Understanding the requirements model in software engineering is like creating a blueprint for a house before it's built. It's a dynamic process that evolves as we learn more about what the system needs to do. Let's break down the key concepts using a simple analogy and examples.
Just like a blueprint helps architects and builders understand how a house will be constructed, the analysis model helps software engineers understand the requirements of a computer-based system. It describes what the system needs to do from different perspectives: informational, functional, and behavioral.
Imagine you're planning a vacation. You create scenarios like "booking a flight," "reserving a hotel," and "renting a car." These scenarios describe how users interact with the system. In software engineering, we use scenarios to create basic use cases and diagrams.
In our vacation planning example, we have different objects like "flight," "hotel," and "car." Each object belongs to a class and has specific attributes and behaviors. Similarly, in software engineering, we categorize objects into classes and define their attributes and behaviors using diagrams like class diagrams.
Think of how your actions change during your vacation, like checking in at the airport or checking out of the hotel. These actions represent the behavior of the system. In software engineering, we use models like state diagrams to represent how the system's behavior changes based on different events or conditions.
Consider the flow of information during your vacation planning, from booking a flight to receiving a confirmation email. Similarly, in software engineering, we model how information flows through the system, from input to processing to output, using flow models.
Just as architects use common design patterns for houses, software engineers use analysis patterns for common problems in software projects. These patterns provide reusable solutions and help speed up the development process. For example, if many projects involve user authentication, we can use a standard pattern for handling user login.
The requirements model is not set in stone. It evolves as we learn more about the system and stakeholders' needs. Some elements become stable over time, while others may change frequently as stakeholders gain a better understanding of their requirements.
Creating an analysis model in software engineering is like creating a roadmap for building a house. It helps us understand what the system needs to do and how it should behave. By using scenarios, class-based elements, behavioral models, flow-oriented elements, and analysis patterns, we can create a comprehensive requirements model that guides the development process. And just like a house blueprint, the requirements model evolves over time as we gain more insights and refine our understanding of the system's needs.
Software refers to the set of programs, data, and instructions that enable computers to perform specific tasks or functions. It encompasses applications, operating systems, and utilities designed to fulfill user needs, enhancing productivity, communication, entertainment, and virtually all aspects of modern life through computational processes and data manipulation.
Software Engineering is the disciplined application of principles, methods, and tools to develop, test, deploy, and maintain high-quality software systems. It involves systematic approaches to problem-solving, project management, and teamwork, aiming to meet user needs efficiently while adhering to standards and best practices throughout the software development lifecycle.